Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94fd25b266edc8792a9fabcfc3e4e583afb683e2ce3078767620b2902fdfee26

Tx prefix hash: ffdc8b2e204b6e590c227125942826f22f075d471d097d26547642adedef9c96
Tx public key: 339714003a3e6e402b3511318df9cb1922f5944210368a95e9af2f23a34a7970
Timestamp: 1706165304 Timestamp [UCT]: 2024-01-25 06:48:24 Age [y:d:h:m:s]: 01:076:17:14:35
Block: 942827 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315932 RingCT/type: yes/0
Extra: 01339714003a3e6e402b3511318df9cb1922f5944210368a95e9af2f23a34a797002110000000a52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 88fb1e70f9e67f55957979b7c8ea9e20bd0ce5189fac41884d5dce2fd6a75a02 0.600000000000 1401005 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": 942837, "vin": [ { "gen": { "height": 942827 } } ], "vout": [ { "amount": 600000000, "target": { "key": "88fb1e70f9e67f55957979b7c8ea9e20bd0ce5189fac41884d5dce2fd6a75a02" } } ], "extra": [ 1, 51, 151, 20, 0, 58, 62, 110, 64, 43, 53, 17, 49, 141, 249, 203, 25, 34, 245, 148, 66, 16, 54, 138, 149, 233, 175, 47, 35, 163, 74, 121, 112, 2, 17, 0, 0, 0, 10, 82, 212, 126, 148, 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