Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31880ccca5b30637eeeed76ef4d99bb4985ab324a0a32b013d22b6cfa984eaea

Tx prefix hash: cb42eef739fdc4705e56d207382d98c34cb3d8b94bbe69aa4115906497e3dc9b
Tx public key: cb40be31279f245c9cc0aee57d8baf1e454d8b8fc176d3d7c9a1a049c08cc799
Timestamp: 1714958259 Timestamp [UCT]: 2024-05-06 01:17:39 Age [y:d:h:m:s]: 00:327:14:04:24
Block: 1015756 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234159 RingCT/type: yes/0
Extra: 01cb40be31279f245c9cc0aee57d8baf1e454d8b8fc176d3d7c9a1a049c08cc7990211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e757aa527e2a55a7b8763e2ac02a24a5ecd0efd11c6d5e1b7c1d91541586daa6 0.600000000000 1479197 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": 1015766, "vin": [ { "gen": { "height": 1015756 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e757aa527e2a55a7b8763e2ac02a24a5ecd0efd11c6d5e1b7c1d91541586daa6" } } ], "extra": [ 1, 203, 64, 190, 49, 39, 159, 36, 92, 156, 192, 174, 229, 125, 139, 175, 30, 69, 77, 139, 143, 193, 118, 211, 215, 201, 161, 160, 73, 192, 140, 199, 153, 2, 17, 0, 0, 0, 2, 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