Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd2bcc62b51871050a830cdc3e2a21c141c9b0933030e7ca7b1630fd2c1356c7

Tx prefix hash: 2e3a0ac25c91059504c01fca95784b6f7092f16e765d2592ab2fcb72e3da09e4
Tx public key: 4df9b4b3d855a86ad3254f78a1683153ff11f0a414fb85bc681e40d37cf4f1d7
Timestamp: 1705401181 Timestamp [UCT]: 2024-01-16 10:33:01 Age [y:d:h:m:s]: 01:085:10:07:29
Block: 936505 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322150 RingCT/type: yes/0
Extra: 014df9b4b3d855a86ad3254f78a1683153ff11f0a414fb85bc681e40d37cf4f1d702110000000179bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8bff9ae3cb12d1c356cc7b6ab5867d362b967d862176375b1b841bf0e8f3ff06 0.600000000000 1394533 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": 936515, "vin": [ { "gen": { "height": 936505 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8bff9ae3cb12d1c356cc7b6ab5867d362b967d862176375b1b841bf0e8f3ff06" } } ], "extra": [ 1, 77, 249, 180, 179, 216, 85, 168, 106, 211, 37, 79, 120, 161, 104, 49, 83, 255, 17, 240, 164, 20, 251, 133, 188, 104, 30, 64, 211, 124, 244, 241, 215, 2, 17, 0, 0, 0, 1, 121, 189, 163, 190, 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