Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64ff2eba8aa725b0be3dff1e57c4d117d942ed1197bda9a91f38002b0cad75cd

Tx prefix hash: aaf608831659f39e1863eb506cc346c738375d6e128d4cc2131c1a6bdff84c9e
Tx public key: 3f2a43c5e0e3f8b189650c6f18f8ada60475ea55cbc85825da1879e6bd5976e8
Timestamp: 1730951787 Timestamp [UCT]: 2024-11-07 03:56:27 Age [y:d:h:m:s]: 00:017:14:06:33
Block: 1148265 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12585 RingCT/type: yes/0
Extra: 013f2a43c5e0e3f8b189650c6f18f8ada60475ea55cbc85825da1879e6bd5976e8021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3553fa7761fd683ba16dfbc09b6c23fce0f93db5b95925e02cf31be7c64dc11f 0.600000000000 1633066 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": 1148275, "vin": [ { "gen": { "height": 1148265 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3553fa7761fd683ba16dfbc09b6c23fce0f93db5b95925e02cf31be7c64dc11f" } } ], "extra": [ 1, 63, 42, 67, 197, 224, 227, 248, 177, 137, 101, 12, 111, 24, 248, 173, 166, 4, 117, 234, 85, 203, 200, 88, 37, 218, 24, 121, 230, 189, 89, 118, 232, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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