Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9df269c04ea84fb8ff2d3212f36a84b87a730942266aeef6f2799f0a0424ec5

Tx prefix hash: aabeded08816061c14acd847271b5da0eab4a05f39fa32349390d1e1a36d8671
Tx public key: 6058f6893b3cc996fe41a89498223be5c978735141a9e809ae07c0e622f5c3a8
Timestamp: 1713607071 Timestamp [UCT]: 2024-04-20 09:57:51 Age [y:d:h:m:s]: 00:251:06:19:32
Block: 1004538 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179861 RingCT/type: yes/0
Extra: 016058f6893b3cc996fe41a89498223be5c978735141a9e809ae07c0e622f5c3a80211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3546d55138084b706356dc90e98e5c557ab631baa2224b6cf4dc6a17fd25abb 0.600000000000 1465106 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": 1004548, "vin": [ { "gen": { "height": 1004538 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3546d55138084b706356dc90e98e5c557ab631baa2224b6cf4dc6a17fd25abb" } } ], "extra": [ 1, 96, 88, 246, 137, 59, 60, 201, 150, 254, 65, 168, 148, 152, 34, 59, 229, 201, 120, 115, 81, 65, 169, 232, 9, 174, 7, 192, 230, 34, 245, 195, 168, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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