Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a978fd672fd529d678dd7bc509d57281ac61fe6a0ac61e4763cece78bc05143

Tx prefix hash: 9ea966a505ef8dd37f5f926688808eb9443ead31331f3ec10c1039c19faf3e8c
Tx public key: 37dd23a01879eefb7ff3357ebfb3e31b72c28f2741450061a61f9b93bf00cc9e
Timestamp: 1719010756 Timestamp [UCT]: 2024-06-21 22:59:16 Age [y:d:h:m:s]: 00:343:11:13:29
Block: 1049337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245507 RingCT/type: yes/0
Extra: 0137dd23a01879eefb7ff3357ebfb3e31b72c28f2741450061a61f9b93bf00cc9e0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5eaa481cb983b099cb992a26ee64782c4dd0f9345c82c3fdf6f685128ec10f4d 0.600000000000 1519436 of 15

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": 1049347, "vin": [ { "gen": { "height": 1049337 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5eaa481cb983b099cb992a26ee64782c4dd0f9345c82c3fdf6f685128ec10f4d" } } ], "extra": [ 1, 55, 221, 35, 160, 24, 121, 238, 251, 127, 243, 53, 126, 191, 179, 227, 27, 114, 194, 143, 39, 65, 69, 0, 97, 166, 31, 155, 147, 191, 0, 204, 158, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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