Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 367c417b24cd673a21f5f1b55fce30334065c57ef16a3844f1a987c577d156b3

Tx prefix hash: 41c22f2525ec65763e5c67b838ede0e2a32d5ec9de5e32a084462e71f8dfceb3
Tx public key: d514d92ac8f6805c29012bbcfc8e5bb8919c274543f42f43a0d9b8f2c56085b2
Timestamp: 1735744423 Timestamp [UCT]: 2025-01-01 15:13:43 Age [y:d:h:m:s]: 00:309:10:29:24
Block: 1187957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218644 RingCT/type: yes/0
Extra: 01d514d92ac8f6805c29012bbcfc8e5bb8919c274543f42f43a0d9b8f2c56085b20211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 47afe80168f45a450d9cc47dd1284e53063f819a6cd28030e494d929dcd53eca 0.600000000000 1674456 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": 1187967, "vin": [ { "gen": { "height": 1187957 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47afe80168f45a450d9cc47dd1284e53063f819a6cd28030e494d929dcd53eca" } } ], "extra": [ 1, 213, 20, 217, 42, 200, 246, 128, 92, 41, 1, 43, 188, 252, 142, 91, 184, 145, 156, 39, 69, 67, 244, 47, 67, 160, 217, 184, 242, 197, 96, 133, 178, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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