Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8babdf0e725015ea5ee1dc058420e044edbcd8a2ab9fa46c2b97a0e16ef0c42e

Tx prefix hash: f0c1efc0be64d5042afbcf3970d95d18048bc3fac913a5390e78a623123969e2
Tx public key: 852abb2ec6dfc36059b4557f1f9825ef35b2d98512ca1694f5cc55d427badf91
Timestamp: 1718297019 Timestamp [UCT]: 2024-06-13 16:43:39 Age [y:d:h:m:s]: 00:225:08:32:48
Block: 1043435 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161234 RingCT/type: yes/0
Extra: 01852abb2ec6dfc36059b4557f1f9825ef35b2d98512ca1694f5cc55d427badf910211000000028fda9b2d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ba782ecc294e606b5974b141caa2c6065189a2d85214e7c0a09e6d4c3c0d71c 0.600000000000 1512588 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": 1043445, "vin": [ { "gen": { "height": 1043435 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ba782ecc294e606b5974b141caa2c6065189a2d85214e7c0a09e6d4c3c0d71c" } } ], "extra": [ 1, 133, 42, 187, 46, 198, 223, 195, 96, 89, 180, 85, 127, 31, 152, 37, 239, 53, 178, 217, 133, 18, 202, 22, 148, 245, 204, 85, 212, 39, 186, 223, 145, 2, 17, 0, 0, 0, 2, 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