Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 3e7a58ac7d8ddc6c4bee2a48cf0197c14753c8c110eba3f5cff08a5fc1587fcc

Tx prefix hash: a118bd6021c01d141f94d02f8af5e6bdb9d1dd018708db45cb0567b5393ee496
Tx public key: 2e717d9bd80b55245ad1b5e9def80ff05180c022790e0bed62f1da56a17bbb9f
Timestamp: 1728956852 Timestamp [UCT]: 2024-10-15 01:47:32 Age [y:d:h:m:s]: 00:184:03:11:57
Block: 1131811 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131387 RingCT/type: yes/0
Extra: 012e717d9bd80b55245ad1b5e9def80ff05180c022790e0bed62f1da56a17bbb9f021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2512254e343c7de621551f7fc2cf447d6cfa74b2158162984f66bcf91e3f7f10 0.600000000000 1614718 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1131821, "vin": [ { "gen": { "height": 1131811 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2512254e343c7de621551f7fc2cf447d6cfa74b2158162984f66bcf91e3f7f10" } } ], "extra": [ 1, 46, 113, 125, 155, 216, 11, 85, 36, 90, 209, 181, 233, 222, 248, 15, 240, 81, 128, 192, 34, 121, 14, 11, 237, 98, 241, 218, 86, 161, 123, 187, 159, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8