Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c53a55487d259196fdb4dea1b45dc2b9117367e6a144f8bd58ddbc220a942a6

Tx prefix hash: bb223a377a9d0fea83e8c37c7ff88233046c9829793f5bf54d63c58b98027889
Tx public key: 817fd1f615e14d8a5e5a1b3e801dae147e2bb8b27a11af1c278d79c1b15fb0b8
Timestamp: 1711738240 Timestamp [UCT]: 2024-03-29 18:50:40 Age [y:d:h:m:s]: 00:301:04:27:54
Block: 989083 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215519 RingCT/type: yes/0
Extra: 01817fd1f615e14d8a5e5a1b3e801dae147e2bb8b27a11af1c278d79c1b15fb0b802110000000141ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6af04bde8c33583ece91020fa337e9955ca42f33298868a05f350bf8303d80e1 0.600000000000 1449378 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": 989093, "vin": [ { "gen": { "height": 989083 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6af04bde8c33583ece91020fa337e9955ca42f33298868a05f350bf8303d80e1" } } ], "extra": [ 1, 129, 127, 209, 246, 21, 225, 77, 138, 94, 90, 27, 62, 128, 29, 174, 20, 126, 43, 184, 178, 122, 17, 175, 28, 39, 141, 121, 193, 177, 95, 176, 184, 2, 17, 0, 0, 0, 1, 65, 238, 28, 155, 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