Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a31c4d03c2181c7b857d3f67ed63866c761083a5b49acfc680c7d96019ec29a9

Tx prefix hash: 007f28a345e4a0cb6ea730dcb7581848e137c4a8c235434e3d35883efde7a625
Tx public key: 063a5fa7b516f41ed321a3fac594dced4fc69e16c88c6145ad20c4af9db6b426
Timestamp: 1736199990 Timestamp [UCT]: 2025-01-06 21:46:30 Age [y:d:h:m:s]: 00:297:18:48:48
Block: 1191718 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210334 RingCT/type: yes/0
Extra: 01063a5fa7b516f41ed321a3fac594dced4fc69e16c88c6145ad20c4af9db6b426021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d01ede9b8d4e9c7a8f7372301438d3bcf060b23e33af2ed0f1a0af7ce45f3c20 0.600000000000 1678259 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": 1191728, "vin": [ { "gen": { "height": 1191718 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d01ede9b8d4e9c7a8f7372301438d3bcf060b23e33af2ed0f1a0af7ce45f3c20" } } ], "extra": [ 1, 6, 58, 95, 167, 181, 22, 244, 30, 211, 33, 163, 250, 197, 148, 220, 237, 79, 198, 158, 22, 200, 140, 97, 69, 173, 32, 196, 175, 157, 182, 180, 38, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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