Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 436a19b8417d8bf4d7f09cad93b58f4d9b8a41d3007e15e5e3cf682f2da68217

Tx prefix hash: f7f52b27049369c3795c6b24812fc47c3c74185549f9dd4a0ea76e2d6b14a5d9
Tx public key: a0d201311c8a31785fec856ae95158f5bff33c3d190ac29f57124a3c7fccc4bd
Timestamp: 1716065398 Timestamp [UCT]: 2024-05-18 20:49:58 Age [y:d:h:m:s]: 00:329:07:00:56
Block: 1024931 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235367 RingCT/type: yes/0
Extra: 01a0d201311c8a31785fec856ae95158f5bff33c3d190ac29f57124a3c7fccc4bd0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6833eb9c691d8d26c01d13adaebf7b9a4c793c3320125004d794618a282c171e 0.600000000000 1491062 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": 1024941, "vin": [ { "gen": { "height": 1024931 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6833eb9c691d8d26c01d13adaebf7b9a4c793c3320125004d794618a282c171e" } } ], "extra": [ 1, 160, 210, 1, 49, 28, 138, 49, 120, 95, 236, 133, 106, 233, 81, 88, 245, 191, 243, 60, 61, 25, 10, 194, 159, 87, 18, 74, 60, 127, 204, 196, 189, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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