Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9083c130a21f2ef2711f141542b96f4b633b6252c0e9c5ae96c06b0b430495c9

Tx prefix hash: 59ac1afd66074f39456fc085941692c327ab524e92ec66fb45190acae898bcd9
Tx public key: 830daad423498e46763238934b3752231a0d9c3fcf1ae08f36bfd35aefc1f9e9
Timestamp: 1716096268 Timestamp [UCT]: 2024-05-19 05:24:28 Age [y:d:h:m:s]: 00:189:08:21:55
Block: 1025193 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135533 RingCT/type: yes/0
Extra: 01830daad423498e46763238934b3752231a0d9c3fcf1ae08f36bfd35aefc1f9e902110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89247dc18f77d596a8b1e3ae66e8e2635ac6a92237d960a70f5e2ce56ff2fa11 0.600000000000 1491512 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": 1025203, "vin": [ { "gen": { "height": 1025193 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89247dc18f77d596a8b1e3ae66e8e2635ac6a92237d960a70f5e2ce56ff2fa11" } } ], "extra": [ 1, 131, 13, 170, 212, 35, 73, 142, 70, 118, 50, 56, 147, 75, 55, 82, 35, 26, 13, 156, 63, 207, 26, 224, 143, 54, 191, 211, 90, 239, 193, 249, 233, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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