Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 807556a89cbc3b10930fa08fc31ba55519a6fb191ced42b0d61e085a1bdc9786

Tx prefix hash: 5940051bf4c9b1fc4f1d7f07fb1460793a504bdc8a1faf95ded38bc03aa12f3f
Tx public key: 9d2273743f856962eb1f8aa9f968c7d054f73fc0dd86d4c28bea91ac0c3b0025
Timestamp: 1695350970 Timestamp [UCT]: 2023-09-22 02:49:30 Age [y:d:h:m:s]: 01:111:02:40:40
Block: 853397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340706 RingCT/type: yes/0
Extra: 019d2273743f856962eb1f8aa9f968c7d054f73fc0dd86d4c28bea91ac0c3b002502110000000233af99f4000000000000000000

1 output(s) for total of 0.912728326000 dcy

stealth address amount amount idx
00: 351e6696ddd098466a8766dc5b4925651208104ec6294e3b6418f2aa6dc6f816 0.912728326000 1307301 of 0

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": 853407, "vin": [ { "gen": { "height": 853397 } } ], "vout": [ { "amount": 912728326, "target": { "key": "351e6696ddd098466a8766dc5b4925651208104ec6294e3b6418f2aa6dc6f816" } } ], "extra": [ 1, 157, 34, 115, 116, 63, 133, 105, 98, 235, 31, 138, 169, 249, 104, 199, 208, 84, 247, 63, 192, 221, 134, 212, 194, 139, 234, 145, 172, 12, 59, 0, 37, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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