Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c198a8a0867abb40aa0d0b169000e2475d1910c5a36889e6a6228fcc51eedfb2

Tx prefix hash: 211fe73310187a28541697eb7d5017a55738bdf61b76c7f898ca84da990d96ca
Tx public key: e8d27ee2e632286ade9eec0c81978d897e8be742dc0b806ef2df6ea4ab94a70a
Timestamp: 1682225724 Timestamp [UCT]: 2023-04-23 04:55:24 Age [y:d:h:m:s]: 01:275:22:20:02
Block: 744637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 458652 RingCT/type: yes/0
Extra: 01e8d27ee2e632286ade9eec0c81978d897e8be742dc0b806ef2df6ea4ab94a70a021100000003b3164c24000000000000000000

1 output(s) for total of 2.092708395000 dcy

stealth address amount amount idx
00: fd8b364e115bad0ee9c1e13fdb43005c338f02ef70a4deb1f9221d10b2d6e26c 2.092708395000 1191992 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": 744647, "vin": [ { "gen": { "height": 744637 } } ], "vout": [ { "amount": 2092708395, "target": { "key": "fd8b364e115bad0ee9c1e13fdb43005c338f02ef70a4deb1f9221d10b2d6e26c" } } ], "extra": [ 1, 232, 210, 126, 226, 230, 50, 40, 106, 222, 158, 236, 12, 129, 151, 141, 137, 126, 139, 231, 66, 220, 11, 128, 110, 242, 223, 110, 164, 171, 148, 167, 10, 2, 17, 0, 0, 0, 3, 179, 22, 76, 36, 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