Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c36f3344a85b5fe982af7377be7d9cd1a09a74edf90ce755020df38c7538de9

Tx prefix hash: 78e74e8e3d49ada40e7a88a0f86d397a1cbda443a5008df8dfc4aaface620c7b
Tx public key: 79fc14eda219751fd276fc1676eb22b3f3220f868cffde68bd2950f9bc6a4839
Timestamp: 1712593084 Timestamp [UCT]: 2024-04-08 16:18:04 Age [y:d:h:m:s]: 00:321:19:52:06
Block: 996116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230092 RingCT/type: yes/0
Extra: 0179fc14eda219751fd276fc1676eb22b3f3220f868cffde68bd2950f9bc6a483902110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf5a4a534b3cdff4dd9eceee2fc5c36c7d0647b20f3b3d36206c340b33f087ba 0.600000000000 1456532 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": 996126, "vin": [ { "gen": { "height": 996116 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf5a4a534b3cdff4dd9eceee2fc5c36c7d0647b20f3b3d36206c340b33f087ba" } } ], "extra": [ 1, 121, 252, 20, 237, 162, 25, 117, 31, 210, 118, 252, 22, 118, 235, 34, 179, 243, 34, 15, 134, 140, 255, 222, 104, 189, 41, 80, 249, 188, 106, 72, 57, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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