Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69e2d7c0352236d3b0c5c1224e9952068257a0e466273498c933013ddb6a31de

Tx prefix hash: 1ae2feb61dc30b0e6a7d05b9c391f544e335f520b803b1493fe744feac179597
Tx public key: f5028e25fd61155495984f7281bb7c927f57a28e6ee6c78b69c8711f3c2179d7
Timestamp: 1739134214 Timestamp [UCT]: 2025-02-09 20:50:14 Age [y:d:h:m:s]: 00:297:05:57:17
Block: 1215755 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210217 RingCT/type: yes/0
Extra: 01f5028e25fd61155495984f7281bb7c927f57a28e6ee6c78b69c8711f3c2179d7021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 324ce1b7618f6d7628776d38fdff5beee66f854a0e30834f00f486eb31e2f76c 0.600000000000 1702554 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": 1215765, "vin": [ { "gen": { "height": 1215755 } } ], "vout": [ { "amount": 600000000, "target": { "key": "324ce1b7618f6d7628776d38fdff5beee66f854a0e30834f00f486eb31e2f76c" } } ], "extra": [ 1, 245, 2, 142, 37, 253, 97, 21, 84, 149, 152, 79, 114, 129, 187, 124, 146, 127, 87, 162, 142, 110, 230, 199, 139, 105, 200, 113, 31, 60, 33, 121, 215, 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