Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bd84d315856fbd4a3828f033a614771d66941fc97114a2fe1759c63530752c2

Tx prefix hash: 3c445153a8a7f0e6bc32bdab3fab03eaecdff0a4feba4cc57c4e774d4f8a6110
Tx public key: a797186e242e6d9da6ce5300ce13b4e68890497644e64d5bba5ef045e363241c
Timestamp: 1725036991 Timestamp [UCT]: 2024-08-30 16:56:31 Age [y:d:h:m:s]: 00:114:02:26:52
Block: 1099306 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81652 RingCT/type: yes/0
Extra: 01a797186e242e6d9da6ce5300ce13b4e68890497644e64d5bba5ef045e363241c021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f326bd98667babb5d5fccbc5b5f3a9b29550c8e287c66c7ba44c503a06de9bc 0.600000000000 1575265 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": 1099316, "vin": [ { "gen": { "height": 1099306 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f326bd98667babb5d5fccbc5b5f3a9b29550c8e287c66c7ba44c503a06de9bc" } } ], "extra": [ 1, 167, 151, 24, 110, 36, 46, 109, 157, 166, 206, 83, 0, 206, 19, 180, 230, 136, 144, 73, 118, 68, 230, 77, 91, 186, 94, 240, 69, 227, 99, 36, 28, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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