Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cff2df93c2c8cfd0c89edec0f541255007eebb7ad3ec342598119d9352f85fe7

Tx prefix hash: 90a1da71e6d0a0d03f76249c49775de0a1d14425ab03c628c93ff6e47eebdfc8
Tx public key: 80085c238e562d53212c2de436f8544c2766ac0dbe2e3e775001074aa7d28d32
Timestamp: 1737799185 Timestamp [UCT]: 2025-01-25 09:59:45 Age [y:d:h:m:s]: 00:048:14:45:42
Block: 1204925 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34560 RingCT/type: yes/0
Extra: 0180085c238e562d53212c2de436f8544c2766ac0dbe2e3e775001074aa7d28d32021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1887362a4129078b0ff758bc7b4f29c6d6cf3f71f37f626fa0b7d932414dbe2d 0.600000000000 1691620 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": 1204935, "vin": [ { "gen": { "height": 1204925 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1887362a4129078b0ff758bc7b4f29c6d6cf3f71f37f626fa0b7d932414dbe2d" } } ], "extra": [ 1, 128, 8, 92, 35, 142, 86, 45, 83, 33, 44, 45, 228, 54, 248, 84, 76, 39, 102, 172, 13, 190, 46, 62, 119, 80, 1, 7, 74, 167, 210, 141, 50, 2, 17, 0, 0, 0, 5, 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