Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7fb2451fb99d53e6dfa4c537acdf7a4537781eaf3b3c740f358913840fdc054c

Tx prefix hash: b738c2ac4e6fe05256e9b4139ad307ef476fd1334c92c7cb1fc15da738d4b78e
Tx public key: de1ce43b7808a56bf42155d7a6d55c2c029357f8d87e9258d73280d485a65f85
Timestamp: 1725472283 Timestamp [UCT]: 2024-09-04 17:51:23 Age [y:d:h:m:s]: 00:215:01:21:27
Block: 1102929 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153530 RingCT/type: yes/0
Extra: 01de1ce43b7808a56bf42155d7a6d55c2c029357f8d87e9258d73280d485a65f85021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5523b3eca605b20c9611070de0c0b3dcfa925100b4e21c7a06e84682effee61 0.600000000000 1579554 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": 1102939, "vin": [ { "gen": { "height": 1102929 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5523b3eca605b20c9611070de0c0b3dcfa925100b4e21c7a06e84682effee61" } } ], "extra": [ 1, 222, 28, 228, 59, 120, 8, 165, 107, 244, 33, 85, 215, 166, 213, 92, 44, 2, 147, 87, 248, 216, 126, 146, 88, 215, 50, 128, 212, 133, 166, 95, 133, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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