Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68994cb8f2c3d8f8893da49db78a9520f2a802b6773b918ec5236945551f6029

Tx prefix hash: 16f415c38d3d2b3b3e5f0bf9543707a9168c1d9800a354e056b41b270020ff4f
Tx public key: db9a5f2324fc3061707c6a08ee5e99c918a746732c4944eb5bec246d8fb3d387
Timestamp: 1717789434 Timestamp [UCT]: 2024-06-07 19:43:54 Age [y:d:h:m:s]: 00:230:11:52:19
Block: 1039229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164908 RingCT/type: yes/0
Extra: 01db9a5f2324fc3061707c6a08ee5e99c918a746732c4944eb5bec246d8fb3d3870211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0e9ca45e4eddca01a6375ce1730e2041b1dbb81964c7098b3f9af966237ef29 0.600000000000 1507856 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": 1039239, "vin": [ { "gen": { "height": 1039229 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0e9ca45e4eddca01a6375ce1730e2041b1dbb81964c7098b3f9af966237ef29" } } ], "extra": [ 1, 219, 154, 95, 35, 36, 252, 48, 97, 112, 124, 106, 8, 238, 94, 153, 201, 24, 167, 70, 115, 44, 73, 68, 235, 91, 236, 36, 109, 143, 179, 211, 135, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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