Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1e53aef7fe3f226df7ec70d86f155d634cfc5c06b94996d07325dc5fabece5f

Tx prefix hash: a12fb2290209d299daecbd6399963f0e2117ec1026b5f7d833e65a09770fc1c1
Tx public key: 5a44f04adcf813dc0a9a0bf1fd55c63b5168d140e4303d29ad57d68279c9ec01
Timestamp: 1706497567 Timestamp [UCT]: 2024-01-29 03:06:07 Age [y:d:h:m:s]: 01:028:02:21:53
Block: 945586 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281132 RingCT/type: yes/0
Extra: 015a44f04adcf813dc0a9a0bf1fd55c63b5168d140e4303d29ad57d68279c9ec010211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1f0e58db90ae373304207b63d57e06f20f2469bde372fe4e307017982e2638f 0.600000000000 1403902 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": 945596, "vin": [ { "gen": { "height": 945586 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1f0e58db90ae373304207b63d57e06f20f2469bde372fe4e307017982e2638f" } } ], "extra": [ 1, 90, 68, 240, 74, 220, 248, 19, 220, 10, 154, 11, 241, 253, 85, 198, 59, 81, 104, 209, 64, 228, 48, 61, 41, 173, 87, 214, 130, 121, 201, 236, 1, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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