Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 851406f49d5596e7587c72809e7cd4dfb60d4ab6447f94bc73c64bc7827984ab

Tx prefix hash: 5b97cb14c0c1714399c10cae18e88d269cefae3eb923c5e6d54d3437428e812a
Tx public key: 0279f664a0e0dec0b47013af548f0a92ae78a045d09f77747398bc3c97d5395a
Timestamp: 1705086432 Timestamp [UCT]: 2024-01-12 19:07:12 Age [y:d:h:m:s]: 01:300:21:48:13
Block: 933898 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 473880 RingCT/type: yes/0
Extra: 010279f664a0e0dec0b47013af548f0a92ae78a045d09f77747398bc3c97d5395a02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c121cd4bcf3a71d1897360a5da352b33fe60954e0d7a207e861652334ae9f39 0.600000000000 1391882 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": 933908, "vin": [ { "gen": { "height": 933898 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c121cd4bcf3a71d1897360a5da352b33fe60954e0d7a207e861652334ae9f39" } } ], "extra": [ 1, 2, 121, 246, 100, 160, 224, 222, 192, 180, 112, 19, 175, 84, 143, 10, 146, 174, 120, 160, 69, 208, 159, 119, 116, 115, 152, 188, 60, 151, 213, 57, 90, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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