Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af4beb30f83f121a99db84723ff5348e39af0ddefaa8062ff63fc6ab5de940ce

Tx prefix hash: 753461bdcbda2b0457ebcabce6feb0d2a36f281a6a171c1dfaf1cb031feb2efa
Tx public key: 1f8ff57e58a48e17042775e2a71c42b1c64d779db11606b1a50cbaf7393dad07
Timestamp: 1718402703 Timestamp [UCT]: 2024-06-14 22:05:03 Age [y:d:h:m:s]: 00:257:03:15:43
Block: 1044312 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183715 RingCT/type: yes/0
Extra: 011f8ff57e58a48e17042775e2a71c42b1c64d779db11606b1a50cbaf7393dad070211000000018fda9b2d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d45e74cf400242e4b96cb33e87ff4caeeb83f419b4654205d6b05a82d1ceb0f 0.600000000000 1513589 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": 1044322, "vin": [ { "gen": { "height": 1044312 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d45e74cf400242e4b96cb33e87ff4caeeb83f419b4654205d6b05a82d1ceb0f" } } ], "extra": [ 1, 31, 143, 245, 126, 88, 164, 142, 23, 4, 39, 117, 226, 167, 28, 66, 177, 198, 77, 119, 157, 177, 22, 6, 177, 165, 12, 186, 247, 57, 61, 173, 7, 2, 17, 0, 0, 0, 1, 143, 218, 155, 45, 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