Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9ec6a2933be2b09dee7c57dec4c85eb0eb9e94c4e261ee1c5584a1128a67779

Tx prefix hash: be90dc6fe738277dc91752902f9ecdeb7d8eb57d0b60de1be7206385a2e4c22c
Tx public key: dd62f4307c56ccbddc372d316367ed9a28b8560a689897575fcf0f2ec3fe591f
Timestamp: 1741916493 Timestamp [UCT]: 2025-03-14 01:41:33 Age [y:d:h:m:s]: 00:298:17:43:26
Block: 1238800 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211300 RingCT/type: yes/0
Extra: 01dd62f4307c56ccbddc372d316367ed9a28b8560a689897575fcf0f2ec3fe591f021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93272494e233d2f7d880deea617e096b3734d6a69703ed92e45da9f2f5c80d72 0.600000000000 1725761 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": 1238810, "vin": [ { "gen": { "height": 1238800 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93272494e233d2f7d880deea617e096b3734d6a69703ed92e45da9f2f5c80d72" } } ], "extra": [ 1, 221, 98, 244, 48, 124, 86, 204, 189, 220, 55, 45, 49, 99, 103, 237, 154, 40, 184, 86, 10, 104, 152, 151, 87, 95, 207, 15, 46, 195, 254, 89, 31, 2, 17, 0, 0, 0, 3, 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