Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 281bf9892d389fb6ab5d400df6a3597e1a25ee1bbbf6f855e076c13d58ce5c5e

Tx prefix hash: 350874e4a062aca47f3ca1d9ab5bdb03aa268b8f2dccba8741355386cee4b951
Tx public key: e5d4f4f8e955a88e243f66f331b7449b4ab8447de3fbbadfe1ed769f9261e4d0
Timestamp: 1712986563 Timestamp [UCT]: 2024-04-13 05:36:03 Age [y:d:h:m:s]: 00:364:15:24:28
Block: 999390 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260705 RingCT/type: yes/0
Extra: 01e5d4f4f8e955a88e243f66f331b7449b4ab8447de3fbbadfe1ed769f9261e4d002110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33ef0bb3adfd548055bf6a02e8ff1405a5c5de4e66c19e7471059ac3591b5c0b 0.600000000000 1459868 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": 999400, "vin": [ { "gen": { "height": 999390 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33ef0bb3adfd548055bf6a02e8ff1405a5c5de4e66c19e7471059ac3591b5c0b" } } ], "extra": [ 1, 229, 212, 244, 248, 233, 85, 168, 142, 36, 63, 102, 243, 49, 183, 68, 155, 74, 184, 68, 125, 227, 251, 186, 223, 225, 237, 118, 159, 146, 97, 228, 208, 2, 17, 0, 0, 0, 2, 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