Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc5c2ecfac8ca33899c5762d7a055a4b9cba71d2aeaa6684f6d4e385ef24cd03

Tx prefix hash: 8c2ffdc8874e8e8d921a3a5b460b79dc19ee1dbfd8fe8d66c7f876d47657f9c8
Tx public key: cc3b116ce9ec118b6e6a613ddd73b1381d83c133bd552fafbbbcaa92e1571f04
Timestamp: 1696463553 Timestamp [UCT]: 2023-10-04 23:52:33 Age [y:d:h:m:s]: 02:035:00:44:34
Block: 862622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 544669 RingCT/type: yes/0
Extra: 01cc3b116ce9ec118b6e6a613ddd73b1381d83c133bd552fafbbbcaa92e1571f04021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.850697704000 dcy

stealth address amount amount idx
00: 1506377bfcbdaa18d1effbc30c042a4cfda6a4233e055f3d8fb150cb85d4f0e3 0.850697704000 1317050 of 0

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": 862632, "vin": [ { "gen": { "height": 862622 } } ], "vout": [ { "amount": 850697704, "target": { "key": "1506377bfcbdaa18d1effbc30c042a4cfda6a4233e055f3d8fb150cb85d4f0e3" } } ], "extra": [ 1, 204, 59, 17, 108, 233, 236, 17, 139, 110, 106, 97, 61, 221, 115, 177, 56, 29, 131, 193, 51, 189, 85, 47, 175, 187, 188, 170, 146, 225, 87, 31, 4, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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