Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 357e58eb192f851be276d4e23e643396f048240033443fd071745bdf29fe2fe7

Tx prefix hash: 26aefd6d84ab0e8d714329ba830b7048936bfff052de1ad7b4bc28231f8ad6fb
Tx public key: 0099e14b4d51a9b860edef0fcfed42428766e4ccf1eedc8f077b6e296a02a819
Timestamp: 1736073881 Timestamp [UCT]: 2025-01-05 10:44:41 Age [y:d:h:m:s]: 00:094:11:44:44
Block: 1190693 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67298 RingCT/type: yes/0
Extra: 010099e14b4d51a9b860edef0fcfed42428766e4ccf1eedc8f077b6e296a02a8190211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d78531d0ea6d644d3cc09d1863309530f12bd7b4a358a2784c8de99f56c2e1a 0.600000000000 1677210 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": 1190703, "vin": [ { "gen": { "height": 1190693 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d78531d0ea6d644d3cc09d1863309530f12bd7b4a358a2784c8de99f56c2e1a" } } ], "extra": [ 1, 0, 153, 225, 75, 77, 81, 169, 184, 96, 237, 239, 15, 207, 237, 66, 66, 135, 102, 228, 204, 241, 238, 220, 143, 7, 123, 110, 41, 106, 2, 168, 25, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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