Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1441a597fef622e3597518683a86be209c24cde6949d504cd246c76829b466e5

Tx prefix hash: 9b677c3a219c4b808d80cf32a76d0b11a9af4cfe3d61d50e8087e85dc225c871
Tx public key: 4a8a2e79c93e44a3bdbb47a6c4930b9b84af341dd22f34ac58468cc8ccade565
Timestamp: 1711305281 Timestamp [UCT]: 2024-03-24 18:34:41 Age [y:d:h:m:s]: 01:069:23:53:57
Block: 985491 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311028 RingCT/type: yes/0
Extra: 014a8a2e79c93e44a3bdbb47a6c4930b9b84af341dd22f34ac58468cc8ccade56502110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf61c0d957de69d8d38a1ad34ab1a0093076b2b91ef8b28a6948b1d1613808d1 0.600000000000 1445704 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": 985501, "vin": [ { "gen": { "height": 985491 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf61c0d957de69d8d38a1ad34ab1a0093076b2b91ef8b28a6948b1d1613808d1" } } ], "extra": [ 1, 74, 138, 46, 121, 201, 62, 68, 163, 189, 187, 71, 166, 196, 147, 11, 155, 132, 175, 52, 29, 210, 47, 52, 172, 88, 70, 140, 200, 204, 173, 229, 101, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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