Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3eeef08ffeaa764549a7b81ab48b6309ccfde3fb54ecb324468ac13bb8559430

Tx prefix hash: f3509b651d55d2d4c0c704ae0a1ae3ead3cedd9e4ca1dce55d9754e83d2cc3f2
Tx public key: 2c4b1640de7a214c74bcf657e2135ebbdc3ca0b5cdb3e359710a111be62dcc30
Timestamp: 1637447945 Timestamp [UCT]: 2021-11-20 22:39:05 Age [y:d:h:m:s]: 03:039:05:36:39
Block: 378578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 806896 RingCT/type: yes/0
Extra: 012c4b1640de7a214c74bcf657e2135ebbdc3ca0b5cdb3e359710a111be62dcc30021100000001e59f5d07000000000000000000

1 output(s) for total of 34.168767368000 dcy

stealth address amount amount idx
00: 15a7a7ac394c980ef08b1ecab1eaf9589272357fc43c04215cadfd26de176fe3 34.168767368000 765516 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": 378588, "vin": [ { "gen": { "height": 378578 } } ], "vout": [ { "amount": 34168767368, "target": { "key": "15a7a7ac394c980ef08b1ecab1eaf9589272357fc43c04215cadfd26de176fe3" } } ], "extra": [ 1, 44, 75, 22, 64, 222, 122, 33, 76, 116, 188, 246, 87, 226, 19, 94, 187, 220, 60, 160, 181, 205, 179, 227, 89, 113, 10, 17, 27, 230, 45, 204, 48, 2, 17, 0, 0, 0, 1, 229, 159, 93, 7, 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