Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72aef1f1396dae4450cb277f850be01b0cd2414bd10800288361fc30b2f1fab3

Tx prefix hash: 2e1fafcea0d99813eae6d2f4d5045655ab0fbc80eb73c2cb006a4c4f9665c1f0
Tx public key: 03e671b58c6fd9e4ec117e8c2dcf3b2c35f8a1b7bd2d30432db1d66e76a68edd
Timestamp: 1730459848 Timestamp [UCT]: 2024-11-01 11:17:28 Age [y:d:h:m:s]: 00:150:06:36:46
Block: 1144192 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107227 RingCT/type: yes/0
Extra: 0103e671b58c6fd9e4ec117e8c2dcf3b2c35f8a1b7bd2d30432db1d66e76a68edd0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54a28eeeb464d06d655f3908ccb082f602c270b0e0750a2cbf4eeb44a2702fa3 0.600000000000 1628323 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": 1144202, "vin": [ { "gen": { "height": 1144192 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54a28eeeb464d06d655f3908ccb082f602c270b0e0750a2cbf4eeb44a2702fa3" } } ], "extra": [ 1, 3, 230, 113, 181, 140, 111, 217, 228, 236, 17, 126, 140, 45, 207, 59, 44, 53, 248, 161, 183, 189, 45, 48, 67, 45, 177, 214, 110, 118, 166, 142, 221, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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