Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 856b826ba2e856b1ebe147882e7940b434be74d0781cdcc07ee01081175e6efd

Tx prefix hash: 108a3cf0d7bbb7d2fe7ab918623e01249010dbe13bd2d2fcbf168f2df231dde6
Tx public key: c5fa4e5ab8321890c87ea89d4622855669e28dc1df2c8639e1b21b4b993c68be
Timestamp: 1710172134 Timestamp [UCT]: 2024-03-11 15:48:54 Age [y:d:h:m:s]: 01:065:09:13:05
Block: 976084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307736 RingCT/type: yes/0
Extra: 01c5fa4e5ab8321890c87ea89d4622855669e28dc1df2c8639e1b21b4b993c68be0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: abb089ce8e9496800d41d97288a27d2380b25dfa0a0e89eb89c730ab97b2d70a 0.600000000000 1436073 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": 976094, "vin": [ { "gen": { "height": 976084 } } ], "vout": [ { "amount": 600000000, "target": { "key": "abb089ce8e9496800d41d97288a27d2380b25dfa0a0e89eb89c730ab97b2d70a" } } ], "extra": [ 1, 197, 250, 78, 90, 184, 50, 24, 144, 200, 126, 168, 157, 70, 34, 133, 86, 105, 226, 141, 193, 223, 44, 134, 57, 225, 178, 27, 75, 153, 60, 104, 190, 2, 17, 0, 0, 0, 4, 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