Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c5293ad0f03de04f4c2f336dbbc7b316c5044c0e316a990b1847810cf48b983

Tx prefix hash: 2460c788ba072e48e6e310e0c1e90311071f1143da1f201dac7bf101a192b87a
Tx public key: 6d7785b2a28c61fbcf73ccb1790cf98433f0daf2b74848b27589d5a7674a21b9
Timestamp: 1673956159 Timestamp [UCT]: 2023-01-17 11:49:19 Age [y:d:h:m:s]: 01:303:02:00:39
Block: 676691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 477590 RingCT/type: yes/0
Extra: 016d7785b2a28c61fbcf73ccb1790cf98433f0daf2b74848b27589d5a7674a21b90211000000018b7b6602000000000000000000

1 output(s) for total of 3.514323662000 dcy

stealth address amount amount idx
00: 8b6375347dde60149f7d1f84eb632c65748be83a00a0b0c598efc4f0131ffe40 3.514323662000 1118416 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": 676701, "vin": [ { "gen": { "height": 676691 } } ], "vout": [ { "amount": 3514323662, "target": { "key": "8b6375347dde60149f7d1f84eb632c65748be83a00a0b0c598efc4f0131ffe40" } } ], "extra": [ 1, 109, 119, 133, 178, 162, 140, 97, 251, 207, 115, 204, 177, 121, 12, 249, 132, 51, 240, 218, 242, 183, 72, 72, 178, 117, 137, 213, 167, 103, 74, 33, 185, 2, 17, 0, 0, 0, 1, 139, 123, 102, 2, 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