Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b7489aff71cc500b96e53d0c4ad9f3bbd1e8ab26c57bcaa1970f8ef1bfddb7f

Tx prefix hash: d7a7fd2d59c2b43d3656129c407ac9f1fea8d21ee4ab37390e2b8623163ce240
Tx public key: 3527e412e1fa26a104ad5d8fbdf23ac6ef011eb2138364b610250ac49d688f21
Timestamp: 1705305878 Timestamp [UCT]: 2024-01-15 08:04:38 Age [y:d:h:m:s]: 01:116:12:37:57
Block: 935714 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344407 RingCT/type: yes/0
Extra: 013527e412e1fa26a104ad5d8fbdf23ac6ef011eb2138364b610250ac49d688f210211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: abde3e17d041f8ab4c4c2ccbb46c8468b84e269f10a256e27713ea02ed5a8bad 0.600000000000 1393730 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": 935724, "vin": [ { "gen": { "height": 935714 } } ], "vout": [ { "amount": 600000000, "target": { "key": "abde3e17d041f8ab4c4c2ccbb46c8468b84e269f10a256e27713ea02ed5a8bad" } } ], "extra": [ 1, 53, 39, 228, 18, 225, 250, 38, 161, 4, 173, 93, 143, 189, 242, 58, 198, 239, 1, 30, 178, 19, 131, 100, 182, 16, 37, 10, 196, 157, 104, 143, 33, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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