Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b67e32ef3b51689e1315c7a8cf8ea2140c9ed43d7886a191cdd85144eba98a4

Tx prefix hash: 16d2659fab21d839ecab5a7e3b5285e4aaf64a3fad22d28ad57fec17e7f3fbe5
Tx public key: c6757a029a0ba16570a158bde0b8759c881896d1e3798fc22018bccca1d06644
Timestamp: 1714484980 Timestamp [UCT]: 2024-04-30 13:49:40 Age [y:d:h:m:s]: 01:024:21:12:57
Block: 1011830 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278741 RingCT/type: yes/0
Extra: 01c6757a029a0ba16570a158bde0b8759c881896d1e3798fc22018bccca1d0664402110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7cd694b8d632093cc6a09a4b613c883e6eb6e4c9403d6d746586600f52d5160b 0.600000000000 1474166 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": 1011840, "vin": [ { "gen": { "height": 1011830 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7cd694b8d632093cc6a09a4b613c883e6eb6e4c9403d6d746586600f52d5160b" } } ], "extra": [ 1, 198, 117, 122, 2, 154, 11, 161, 101, 112, 161, 88, 189, 224, 184, 117, 156, 136, 24, 150, 209, 227, 121, 143, 194, 32, 24, 188, 204, 161, 208, 102, 68, 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