Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 684f5d328591d012c597dcf86e82c4b610387f2d07f94b060887b3af395d1d0b

Tx prefix hash: 00da215a509d4fe2230fc529365c43c6ce1cf81a893cdc739c7e215d63bc7dfe
Tx public key: 7fbee78b299f0803396670af969a51b965d389f6b651244df2b6514dabad8e77
Timestamp: 1687329722 Timestamp [UCT]: 2023-06-21 06:42:02 Age [y:d:h:m:s]: 01:209:21:48:32
Block: 786955 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 411403 RingCT/type: yes/0
Extra: 017fbee78b299f0803396670af969a51b965d389f6b651244df2b6514dabad8e77021100000002faf35c9c000000000000000000

1 output(s) for total of 1.515275333000 dcy

stealth address amount amount idx
00: 4d245119b4faa2bf2a11bc934da2fc4ce417351328bd24b4aa4e7830ba2cc0c4 1.515275333000 1236970 of 0

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": 786965, "vin": [ { "gen": { "height": 786955 } } ], "vout": [ { "amount": 1515275333, "target": { "key": "4d245119b4faa2bf2a11bc934da2fc4ce417351328bd24b4aa4e7830ba2cc0c4" } } ], "extra": [ 1, 127, 190, 231, 139, 41, 159, 8, 3, 57, 102, 112, 175, 150, 154, 81, 185, 101, 211, 137, 246, 182, 81, 36, 77, 242, 182, 81, 77, 171, 173, 142, 119, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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