Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c6de7f2f9138f170e01e624e2b8cd465adff9269371a4d586a6e240cb244904

Tx prefix hash: f29eb41574d2f964f3ec32fdd870716dd9cfadb385c525a5ed1fddbb1e9e3acf
Tx public key: 7ed3f1b81f7824e8c32024ef46dbd7ea37c270abe88cd1fb2c7283da6014c17b
Timestamp: 1731142617 Timestamp [UCT]: 2024-11-09 08:56:57 Age [y:d:h:m:s]: 00:200:11:04:42
Block: 1149853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143133 RingCT/type: yes/0
Extra: 017ed3f1b81f7824e8c32024ef46dbd7ea37c270abe88cd1fb2c7283da6014c17b021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba1766ef0ec14635674b0257f8fa0f42d9ea7fc7f650d1302d91fde974a7fa01 0.600000000000 1635020 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": 1149863, "vin": [ { "gen": { "height": 1149853 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba1766ef0ec14635674b0257f8fa0f42d9ea7fc7f650d1302d91fde974a7fa01" } } ], "extra": [ 1, 126, 211, 241, 184, 31, 120, 36, 232, 195, 32, 36, 239, 70, 219, 215, 234, 55, 194, 112, 171, 232, 140, 209, 251, 44, 114, 131, 218, 96, 20, 193, 123, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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