Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf3b3a1a9eeefe8fe5230ed19046d8b85ed6d9db3a6aafa8d91c1f5fa2df5516

Tx prefix hash: 65009e9734140ef49e7502f14d6f7ccf9850c6a241847d1c9403c7c66bac6b76
Tx public key: dc696e54e32b9f19ceeda4ca006e4608ae57f3c4b99704296cb98bfba32bc486
Timestamp: 1722018824 Timestamp [UCT]: 2024-07-26 18:33:44 Age [y:d:h:m:s]: 00:265:05:36:58
Block: 1074286 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189476 RingCT/type: yes/0
Extra: 01dc696e54e32b9f19ceeda4ca006e4608ae57f3c4b99704296cb98bfba32bc48602110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40c9c1f133e2178d27fd94c6c059c2c9b53a7e965eb633f1089a31859145df7a 0.600000000000 1546799 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": 1074296, "vin": [ { "gen": { "height": 1074286 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40c9c1f133e2178d27fd94c6c059c2c9b53a7e965eb633f1089a31859145df7a" } } ], "extra": [ 1, 220, 105, 110, 84, 227, 43, 159, 25, 206, 237, 164, 202, 0, 110, 70, 8, 174, 87, 243, 196, 185, 151, 4, 41, 108, 185, 139, 251, 163, 43, 196, 134, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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