Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 003a2808bf73295104f91eb73a8ab5a0b2eaccafca673c23824c7f884c686ecb

Tx prefix hash: 94a778af99e77783bd783654004cddbefe0037c7c47ba06189f6e4591b964182
Tx public key: 8af7348364c16f793c398f8dfad2f90a8a2bd898b29f4426a851578b544b9849
Timestamp: 1701696444 Timestamp [UCT]: 2023-12-04 13:27:24 Age [y:d:h:m:s]: 01:135:11:25:04
Block: 905801 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357978 RingCT/type: yes/0
Extra: 018af7348364c16f793c398f8dfad2f90a8a2bd898b29f4426a851578b544b984902110000000475e3f0e9000000000000000000

1 output(s) for total of 0.611934933000 dcy

stealth address amount amount idx
00: f045baf21ecca1810e7e0c2c1d00f58c07ef5031db73f057d1ecd73112a6c8a1 0.611934933000 1362716 of 0

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": 905811, "vin": [ { "gen": { "height": 905801 } } ], "vout": [ { "amount": 611934933, "target": { "key": "f045baf21ecca1810e7e0c2c1d00f58c07ef5031db73f057d1ecd73112a6c8a1" } } ], "extra": [ 1, 138, 247, 52, 131, 100, 193, 111, 121, 60, 57, 143, 141, 250, 210, 249, 10, 138, 43, 216, 152, 178, 159, 68, 38, 168, 81, 87, 139, 84, 75, 152, 73, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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