Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 404a3a6267547f6fa4c907794bb7c8c429e725029a86da04da825ef7b2a9e4c5

Tx prefix hash: 369949902cfc0a66777bef6c14fe6f7db0f421f78584c44826093c774985fad7
Tx public key: 07a20d9f7ae0a8813bd5dc3e6453bc82331921e64a5b9b8a2dd64ed8a5c5310e
Timestamp: 1721027060 Timestamp [UCT]: 2024-07-15 07:04:20 Age [y:d:h:m:s]: 00:246:01:55:51
Block: 1066082 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175789 RingCT/type: yes/0
Extra: 0107a20d9f7ae0a8813bd5dc3e6453bc82331921e64a5b9b8a2dd64ed8a5c5310e02110000000de914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4ea45500aa23beea3ab65d55edfda2d13ed9f57b6a4e0215c1f4f9e3908e1a5 0.600000000000 1536653 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": 1066092, "vin": [ { "gen": { "height": 1066082 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4ea45500aa23beea3ab65d55edfda2d13ed9f57b6a4e0215c1f4f9e3908e1a5" } } ], "extra": [ 1, 7, 162, 13, 159, 122, 224, 168, 129, 59, 213, 220, 62, 100, 83, 188, 130, 51, 25, 33, 230, 74, 91, 155, 138, 45, 214, 78, 216, 165, 197, 49, 14, 2, 17, 0, 0, 0, 13, 233, 20, 221, 21, 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