Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4818c806a446be832771d204014fb8b3ad575f8c9af24bd63072b384062f57d4

Tx prefix hash: 0aecca52a46b8c4a55a09ed0591b3b7642e3081809703dcb964f56c710897d3e
Tx public key: a6cd05a0947de877316c9f71a712fb6d49b46c748ca33c77b2d0e161cf899f23
Timestamp: 1582057080 Timestamp [UCT]: 2020-02-18 20:18:00 Age [y:d:h:m:s]: 04:353:19:41:58
Block: 67729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1145017 RingCT/type: yes/0
Extra: 01a6cd05a0947de877316c9f71a712fb6d49b46c748ca33c77b2d0e161cf899f23021100000002d81c26c0000000000000000000

1 output(s) for total of 366.088860641000 dcy

stealth address amount amount idx
00: 515aef3d7442123b1777ce4a3ccb9a4e0fa00f36e70af9b779107f78a26b8bf6 366.088860641000 124738 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": 67739, "vin": [ { "gen": { "height": 67729 } } ], "vout": [ { "amount": 366088860641, "target": { "key": "515aef3d7442123b1777ce4a3ccb9a4e0fa00f36e70af9b779107f78a26b8bf6" } } ], "extra": [ 1, 166, 205, 5, 160, 148, 125, 232, 119, 49, 108, 159, 113, 167, 18, 251, 109, 73, 180, 108, 116, 140, 163, 60, 119, 178, 208, 225, 97, 207, 137, 159, 35, 2, 17, 0, 0, 0, 2, 216, 28, 38, 192, 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