Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0514ad16d45029aa62f720055235d4b95d62efcabc172359f3f170c03664920

Tx prefix hash: b3de38664d00676c8d4148cf7c738dae8ae86ed6e191cc012a465aecb5e582f6
Tx public key: 78b5f3e9572e1e156333f85deb0c00164add5ba42155af25c7919d2bf1ec6f7b
Timestamp: 1657245098 Timestamp [UCT]: 2022-07-08 01:51:38 Age [y:d:h:m:s]: 02:256:08:57:26
Block: 539002 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 704370 RingCT/type: yes/0
Extra: 0178b5f3e9572e1e156333f85deb0c00164add5ba42155af25c7919d2bf1ec6f7b02110000002cbf7ee4e7000000000000000000

1 output(s) for total of 10.047610058000 dcy

stealth address amount amount idx
00: 7d53212280203d50d89a438c3c0e70fd1de6e94de4265adbc39d42dd4b2e41c5 10.047610058000 969061 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": 539012, "vin": [ { "gen": { "height": 539002 } } ], "vout": [ { "amount": 10047610058, "target": { "key": "7d53212280203d50d89a438c3c0e70fd1de6e94de4265adbc39d42dd4b2e41c5" } } ], "extra": [ 1, 120, 181, 243, 233, 87, 46, 30, 21, 99, 51, 248, 93, 235, 12, 0, 22, 74, 221, 91, 164, 33, 85, 175, 37, 199, 145, 157, 43, 241, 236, 111, 123, 2, 17, 0, 0, 0, 44, 191, 126, 228, 231, 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