Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f0a4f3a3bb9c76aa3363376792379c7591fff2c266a5fad949dd1920bdb2a16

Tx prefix hash: ee51fa3360d5fe881a3da162a3971593fd60ccadf52bfb010bbd6fa77a1a730e
Tx public key: 887b7186e1049153f3a5b84e99c6354ec7df3ba999f5e16811d9a648394a8d8b
Timestamp: 1737024703 Timestamp [UCT]: 2025-01-16 10:51:43 Age [y:d:h:m:s]: 00:358:07:56:56
Block: 1198544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253693 RingCT/type: yes/0
Extra: 01887b7186e1049153f3a5b84e99c6354ec7df3ba999f5e16811d9a648394a8d8b021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd586668ed7d88aaf35bdb999a589b3634571c5c08e67c80d226efe8399eb3b4 0.600000000000 1685169 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": 1198554, "vin": [ { "gen": { "height": 1198544 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd586668ed7d88aaf35bdb999a589b3634571c5c08e67c80d226efe8399eb3b4" } } ], "extra": [ 1, 136, 123, 113, 134, 225, 4, 145, 83, 243, 165, 184, 78, 153, 198, 53, 78, 199, 223, 59, 169, 153, 245, 225, 104, 17, 217, 166, 72, 57, 74, 141, 139, 2, 17, 0, 0, 0, 1, 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