Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd367f0258a78bbe0b58bbe73810b8b31475dfb1becc2e438138f038b6638b9e

Tx prefix hash: d98adf6dc16ab6327bac9a65772db00c6d5ace1dd68a371da455c29e6b97f7da
Tx public key: d4a8d1ea7b46f82b14ac18d6abf525c99825ce45ab1327011e602d439a11a0f5
Timestamp: 1735721895 Timestamp [UCT]: 2025-01-01 08:58:15 Age [y:d:h:m:s]: 00:092:06:21:15
Block: 1187765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65727 RingCT/type: yes/0
Extra: 01d4a8d1ea7b46f82b14ac18d6abf525c99825ce45ab1327011e602d439a11a0f5021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fdc7c130f6d7c55cf505fb1ffd2efb74cfd3a86af2a112e5bd594fbebf619114 0.600000000000 1674260 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": 1187775, "vin": [ { "gen": { "height": 1187765 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fdc7c130f6d7c55cf505fb1ffd2efb74cfd3a86af2a112e5bd594fbebf619114" } } ], "extra": [ 1, 212, 168, 209, 234, 123, 70, 248, 43, 20, 172, 24, 214, 171, 245, 37, 201, 152, 37, 206, 69, 171, 19, 39, 1, 30, 96, 45, 67, 154, 17, 160, 245, 2, 17, 0, 0, 0, 2, 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