Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5e00a4758bf84e4a8751980bb97be6104c92e89587d85135e450ff7e58acec3

Tx prefix hash: 7350e58dd404f01e9a978e7d83141e6fb3d61b350d2a5ee19b8793c32d2040c1
Tx public key: 44784dc08fb859254995370c79df974cfe5cdeac7948730622610b94c32625e9
Timestamp: 1699209608 Timestamp [UCT]: 2023-11-05 18:40:08 Age [y:d:h:m:s]: 01:156:09:41:31
Block: 885190 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372986 RingCT/type: yes/0
Extra: 0144784dc08fb859254995370c79df974cfe5cdeac7948730622610b94c32625e9021100000001faf35c9c000000000000000000

1 output(s) for total of 0.716140236000 dcy

stealth address amount amount idx
00: 04e51207be05f1819d207e13e5d9e88b215e5483c9a21c28f529707ac2b22f30 0.716140236000 1340947 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": 885200, "vin": [ { "gen": { "height": 885190 } } ], "vout": [ { "amount": 716140236, "target": { "key": "04e51207be05f1819d207e13e5d9e88b215e5483c9a21c28f529707ac2b22f30" } } ], "extra": [ 1, 68, 120, 77, 192, 143, 184, 89, 37, 73, 149, 55, 12, 121, 223, 151, 76, 254, 92, 222, 172, 121, 72, 115, 6, 34, 97, 11, 148, 195, 38, 37, 233, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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