Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59e1a3987a18d7d6056a961a97652ed19b889b7b37433ad3876253e35eebe1ad

Tx prefix hash: 34b03cbbc3cd387ee3c4f6dc9001aa5c81ea27bc85902238e8f2256a89450941
Tx public key: fd7c9644ab71b1b07bbc6f45e7b7c45af175b77d23aa383235feb130f9175936
Timestamp: 1735644327 Timestamp [UCT]: 2024-12-31 11:25:27 Age [y:d:h:m:s]: 00:125:17:39:17
Block: 1187123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89667 RingCT/type: yes/0
Extra: 01fd7c9644ab71b1b07bbc6f45e7b7c45af175b77d23aa383235feb130f9175936021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc266ed5d160189614d8c5fb964dc9192ba2a8f3df3cc02ec13faa2abef424eb 0.600000000000 1673610 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": 1187133, "vin": [ { "gen": { "height": 1187123 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc266ed5d160189614d8c5fb964dc9192ba2a8f3df3cc02ec13faa2abef424eb" } } ], "extra": [ 1, 253, 124, 150, 68, 171, 113, 177, 176, 123, 188, 111, 69, 231, 183, 196, 90, 241, 117, 183, 125, 35, 170, 56, 50, 53, 254, 177, 48, 249, 23, 89, 54, 2, 17, 0, 0, 0, 8, 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