Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0dd53ed14565ad702ca4d0c6d86313a3d80300a220264b19d61341f9a98644e0

Tx prefix hash: 48457d331bd7d25065fee8ddf59db09eaa81dba1f64fc5583dabf156e23e0f84
Tx public key: a3dce55ee5e26a5ae66d1e05136f544b866880b7526f9ddc84447584c9113b9b
Timestamp: 1690544456 Timestamp [UCT]: 2023-07-28 11:40:56 Age [y:d:h:m:s]: 01:244:06:47:37
Block: 813630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 435666 RingCT/type: yes/0
Extra: 01a3dce55ee5e26a5ae66d1e05136f544b866880b7526f9ddc84447584c9113b9b02110000000433af99f4000000000000000000

1 output(s) for total of 1.236249606000 dcy

stealth address amount amount idx
00: fb0ef4b856903564b9c0f4013fdfe3929fac3f3e0fdb8a5b70e50c53a9c218be 1.236249606000 1265373 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": 813640, "vin": [ { "gen": { "height": 813630 } } ], "vout": [ { "amount": 1236249606, "target": { "key": "fb0ef4b856903564b9c0f4013fdfe3929fac3f3e0fdb8a5b70e50c53a9c218be" } } ], "extra": [ 1, 163, 220, 229, 94, 229, 226, 106, 90, 230, 109, 30, 5, 19, 111, 84, 75, 134, 104, 128, 183, 82, 111, 157, 220, 132, 68, 117, 132, 201, 17, 59, 155, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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