Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eded6fa435aaed4e6561d0edb51cea0f5f2dc65ab2d7e11462229241f3fe041c

Tx prefix hash: bceb0e6d213f9bba6ea5a051fa2cd38ca7165faae21cb60c0176ca60175d1ae0
Tx public key: eef860fc035a7cbd05e773a36e0e391887c02aef82463618fc45be7189390e6d
Timestamp: 1636681736 Timestamp [UCT]: 2021-11-12 01:48:56 Age [y:d:h:m:s]: 03:167:10:15:29
Block: 372490 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 898082 RingCT/type: yes/0
Extra: 01eef860fc035a7cbd05e773a36e0e391887c02aef82463618fc45be7189390e6d02110000000ca272b9cb000000000000000000

1 output(s) for total of 35.792035103000 dcy

stealth address amount amount idx
00: b46854168f1c1f0168e4ae5d1ae7c8a5fa4a796595ed3087a8f4c77cf55715c9 35.792035103000 754546 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": 372500, "vin": [ { "gen": { "height": 372490 } } ], "vout": [ { "amount": 35792035103, "target": { "key": "b46854168f1c1f0168e4ae5d1ae7c8a5fa4a796595ed3087a8f4c77cf55715c9" } } ], "extra": [ 1, 238, 248, 96, 252, 3, 90, 124, 189, 5, 231, 115, 163, 110, 14, 57, 24, 135, 192, 42, 239, 130, 70, 54, 24, 252, 69, 190, 113, 137, 57, 14, 109, 2, 17, 0, 0, 0, 12, 162, 114, 185, 203, 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