Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a132b7021703e79f225a5df9d2be4234ff0813f3ee77bea90f884b6005e1f4fb

Tx prefix hash: 7959a05cb583a242e6cf1130452e9977cd3bf9d46ba295e13faf2b1d4d583463
Tx public key: a1b7e79e6395e13bb218ddce896750f0a3d2b0054f81bc2240f231ee15f62ee1
Timestamp: 1682543020 Timestamp [UCT]: 2023-04-26 21:03:40 Age [y:d:h:m:s]: 01:344:00:28:57
Block: 747264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 507123 RingCT/type: yes/0
Extra: 01a1b7e79e6395e13bb218ddce896750f0a3d2b0054f81bc2240f231ee15f62ee1021100000002e6d27f9c000000000000000000

1 output(s) for total of 2.051182824000 dcy

stealth address amount amount idx
00: 96910df3a9a8b5e3c17005b0d7ff4cbdfe3cfa886bc33a5c1e0769a8b6cb8726 2.051182824000 1194917 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": 747274, "vin": [ { "gen": { "height": 747264 } } ], "vout": [ { "amount": 2051182824, "target": { "key": "96910df3a9a8b5e3c17005b0d7ff4cbdfe3cfa886bc33a5c1e0769a8b6cb8726" } } ], "extra": [ 1, 161, 183, 231, 158, 99, 149, 225, 59, 178, 24, 221, 206, 137, 103, 80, 240, 163, 210, 176, 5, 79, 129, 188, 34, 64, 242, 49, 238, 21, 246, 46, 225, 2, 17, 0, 0, 0, 2, 230, 210, 127, 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