Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc4c776d416491bfb92235e962637e335484db21813ce647e7d148d552612055

Tx prefix hash: 61f0af8566abb4783de46f7e7fadbd6e1cd3c64e1ce96d0df9c0d102d1c9fcde
Tx public key: d4b63f23c1c45cfae1336cd591acd647938f13f91a21ca4cefddf12311f37603
Timestamp: 1733697084 Timestamp [UCT]: 2024-12-08 22:31:24 Age [y:d:h:m:s]: 00:099:09:19:32
Block: 1171030 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70802 RingCT/type: yes/0
Extra: 01d4b63f23c1c45cfae1336cd591acd647938f13f91a21ca4cefddf12311f3760302110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: feb2eaec0c20b4a4e1848e0400c196d6440677a72a3b085274d8c32a7ab5eb35 0.600000000000 1656765 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": 1171040, "vin": [ { "gen": { "height": 1171030 } } ], "vout": [ { "amount": 600000000, "target": { "key": "feb2eaec0c20b4a4e1848e0400c196d6440677a72a3b085274d8c32a7ab5eb35" } } ], "extra": [ 1, 212, 182, 63, 35, 193, 196, 92, 250, 225, 51, 108, 213, 145, 172, 214, 71, 147, 143, 19, 249, 26, 33, 202, 76, 239, 221, 241, 35, 17, 243, 118, 3, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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