Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a495d28f3397a6ccaf131334c026709ba0ef7b43f1c12468253b8e0aed7916b

Tx prefix hash: 4535b63d91f1f1afa7c5418a23a0b7dc414d220dd0d4e57785939bf61351be8c
Tx public key: 24d8aaa3b70b1330d9f4f4ff33aac940beaf2232a0c9ac2beb7258efd5b0e92c
Timestamp: 1725182632 Timestamp [UCT]: 2024-09-01 09:23:52 Age [y:d:h:m:s]: 00:196:19:34:36
Block: 1100523 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140518 RingCT/type: yes/0
Extra: 0124d8aaa3b70b1330d9f4f4ff33aac940beaf2232a0c9ac2beb7258efd5b0e92c021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b7a1d9c9e1ce098d3d73f505a62b2cb2505d01fdefbe466633f748d5ee1ebea 0.600000000000 1576502 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": 1100533, "vin": [ { "gen": { "height": 1100523 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b7a1d9c9e1ce098d3d73f505a62b2cb2505d01fdefbe466633f748d5ee1ebea" } } ], "extra": [ 1, 36, 216, 170, 163, 183, 11, 19, 48, 217, 244, 244, 255, 51, 170, 201, 64, 190, 175, 34, 50, 160, 201, 172, 43, 235, 114, 88, 239, 213, 176, 233, 44, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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