Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6660266250a1c8d7857093068df26152ca9ff255b6e244b5d413f1897fef43a5

Tx prefix hash: 8540d67b6206dca19b209e16ab168c1fd4c3839cec32da3bb01d94a223aa8f9c
Tx public key: 2e500d086bac20575ee2e475f15ba1ca38aa6a27087b9b18b0a8870eb9b56ad0
Timestamp: 1724527284 Timestamp [UCT]: 2024-08-24 19:21:24 Age [y:d:h:m:s]: 00:222:01:26:46
Block: 1095101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158552 RingCT/type: yes/0
Extra: 012e500d086bac20575ee2e475f15ba1ca38aa6a27087b9b18b0a8870eb9b56ad0021100000001e337358e000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 834788879c1517dc240fc5e50382db2e6dc1d7c002fbadc8fdb03948c32500ef 0.600000000000 1570242 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": 1095111, "vin": [ { "gen": { "height": 1095101 } } ], "vout": [ { "amount": 600000000, "target": { "key": "834788879c1517dc240fc5e50382db2e6dc1d7c002fbadc8fdb03948c32500ef" } } ], "extra": [ 1, 46, 80, 13, 8, 107, 172, 32, 87, 94, 226, 228, 117, 241, 91, 161, 202, 56, 170, 106, 39, 8, 123, 155, 24, 176, 168, 135, 14, 185, 181, 106, 208, 2, 17, 0, 0, 0, 1, 227, 55, 53, 142, 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