Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1196b8f681e9430ed87e53de260d2e3769df22a53b668a5c2b07ceb3ed67ee0

Tx prefix hash: c5191c088a64b8f720d79cb80f96a8106fca9cc80bcf84c9893c4bde030e9244
Tx public key: 0a73307f3fafee520b3ec33027a26a825c400f394edb6144277a9276806a4b2c
Timestamp: 1651171503 Timestamp [UCT]: 2022-04-28 18:45:03 Age [y:d:h:m:s]: 02:324:13:00:43
Block: 490107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 751724 RingCT/type: yes/0
Extra: 010a73307f3fafee520b3ec33027a26a825c400f394edb6144277a9276806a4b2c02110000000cc9067537000000000000000000

1 output(s) for total of 14.590570584000 dcy

stealth address amount amount idx
00: b15a2b00073b1dd976605944078945841c8fd2e1d735b3e2243d62155a2bf3fd 14.590570584000 913044 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": 490117, "vin": [ { "gen": { "height": 490107 } } ], "vout": [ { "amount": 14590570584, "target": { "key": "b15a2b00073b1dd976605944078945841c8fd2e1d735b3e2243d62155a2bf3fd" } } ], "extra": [ 1, 10, 115, 48, 127, 63, 175, 238, 82, 11, 62, 195, 48, 39, 162, 106, 130, 92, 64, 15, 57, 78, 219, 97, 68, 39, 122, 146, 118, 128, 106, 75, 44, 2, 17, 0, 0, 0, 12, 201, 6, 117, 55, 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