Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4655a50e5fdef09fd33292abd44ca27a5b1911f56f2edd305881f22f7ba6d302

Tx prefix hash: b34058960457cc345581761ba58bb2dcd46cf3d2f3e1132ccc2710c4fe446cc0
Tx public key: bd704314acb4a31141a3afe0c7d1a1cfcd4ab5775c8e4713edf7a4e444d6bb3f
Timestamp: 1698635749 Timestamp [UCT]: 2023-10-30 03:15:49 Age [y:d:h:m:s]: 01:231:02:43:54
Block: 880646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 426109 RingCT/type: yes/0
Extra: 01bd704314acb4a31141a3afe0c7d1a1cfcd4ab5775c8e4713edf7a4e444d6bb3f021100000003faf35c9c000000000000000000

1 output(s) for total of 0.741402831000 dcy

stealth address amount amount idx
00: 6b4d20665f186aef06f32f1e1a566c17920764113e4f4e6970f252f5d125d215 0.741402831000 1336210 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": 880656, "vin": [ { "gen": { "height": 880646 } } ], "vout": [ { "amount": 741402831, "target": { "key": "6b4d20665f186aef06f32f1e1a566c17920764113e4f4e6970f252f5d125d215" } } ], "extra": [ 1, 189, 112, 67, 20, 172, 180, 163, 17, 65, 163, 175, 224, 199, 209, 161, 207, 205, 74, 181, 119, 92, 142, 71, 19, 237, 247, 164, 228, 68, 214, 187, 63, 2, 17, 0, 0, 0, 3, 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