Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81040c55c845c3558ca7ffcae48122fc1cdbbb52a38ba870434b5004c56d0ae3

Tx prefix hash: d10a5986769af713ba2413b8bc7c1fb7717dc40ea3cb70221bfd22d3ad2cf1e7
Tx public key: 7345c6b985e8e418c052037ae56c1456206d5f10643f37cc227272fb2db3da08
Timestamp: 1649574590 Timestamp [UCT]: 2022-04-10 07:09:50 Age [y:d:h:m:s]: 02:263:03:37:04
Block: 477114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 707847 RingCT/type: yes/0
Extra: 017345c6b985e8e418c052037ae56c1456206d5f10643f37cc227272fb2db3da0802110000000ebf7ee4e7000000000000000000

1 output(s) for total of 16.111037095000 dcy

stealth address amount amount idx
00: 09bafca9ad66280967b156f6fdf7cb7d4db2e1b56395996ba1ba12498c51acd6 16.111037095000 897737 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": 477124, "vin": [ { "gen": { "height": 477114 } } ], "vout": [ { "amount": 16111037095, "target": { "key": "09bafca9ad66280967b156f6fdf7cb7d4db2e1b56395996ba1ba12498c51acd6" } } ], "extra": [ 1, 115, 69, 198, 185, 133, 232, 228, 24, 192, 82, 3, 122, 229, 108, 20, 86, 32, 109, 95, 16, 100, 63, 55, 204, 34, 114, 114, 251, 45, 179, 218, 8, 2, 17, 0, 0, 0, 14, 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