Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e392a5e7670f558fe24c35cef94467b32173e5a5597d861c8a8dff034e1b8ffd

Tx prefix hash: 3ac61d5084215cda926331b9d985e73afa42b89d17c272c9334477d83f1925ae
Tx public key: f71754e8fc090a7db58fc6e1bdd6df51e4046c7e97513e4fa2ea2d1465a595a2
Timestamp: 1693273413 Timestamp [UCT]: 2023-08-29 01:43:33 Age [y:d:h:m:s]: 01:126:10:29:08
Block: 836159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351704 RingCT/type: yes/0
Extra: 01f71754e8fc090a7db58fc6e1bdd6df51e4046c7e97513e4fa2ea2d1465a595a2021100000009d4dbf7b9000000000000000000

1 output(s) for total of 1.041017916000 dcy

stealth address amount amount idx
00: 86782c41afd1ac4673ec9c7341903f7e104a7a135cf62a3dc67b64d41bd82963 1.041017916000 1288737 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": 836169, "vin": [ { "gen": { "height": 836159 } } ], "vout": [ { "amount": 1041017916, "target": { "key": "86782c41afd1ac4673ec9c7341903f7e104a7a135cf62a3dc67b64d41bd82963" } } ], "extra": [ 1, 247, 23, 84, 232, 252, 9, 10, 125, 181, 143, 198, 225, 189, 214, 223, 81, 228, 4, 108, 126, 151, 81, 62, 79, 162, 234, 45, 20, 101, 165, 149, 162, 2, 17, 0, 0, 0, 9, 212, 219, 247, 185, 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