Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b92c9aa3d72561a859f99f7a3e0e999952eb227616c1331e87d41f4d0b95ae9

Tx prefix hash: eb5263b5ffd722d2e3b57315187b0a33d59911d153c9f594e945a6f1aac97b29
Tx public key: 7e23dc8ace6061ed266cde15b38f821b87a798300f6c6c1d66e74369576fb632
Timestamp: 1745390563 Timestamp [UCT]: 2025-04-23 06:42:43 Age [y:d:h:m:s]: 00:259:06:57:27
Block: 1267535 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183114 RingCT/type: yes/0
Extra: 017e23dc8ace6061ed266cde15b38f821b87a798300f6c6c1d66e74369576fb632021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59746d4aae9328b92ec218826809c1989e2880678e6cf43007685d53a7c93e16 0.600000000000 1754764 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": 1267545, "vin": [ { "gen": { "height": 1267535 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59746d4aae9328b92ec218826809c1989e2880678e6cf43007685d53a7c93e16" } } ], "extra": [ 1, 126, 35, 220, 138, 206, 96, 97, 237, 38, 108, 222, 21, 179, 143, 130, 27, 135, 167, 152, 48, 15, 108, 108, 29, 102, 231, 67, 105, 87, 111, 182, 50, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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