Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 379e9db9d2fbef993aa08d7f0b988af0ce0ff916ca47915e5c6471fbbbd6c1f3

Tx prefix hash: bc2c4db694b2862bafb800c23edecd2622286bac70f2ae57d41effa01ec33e46
Tx public key: 56a59fd37f752b7ddea91355f983625812bf7aa5e7a04b79b8335ca80743b69b
Timestamp: 1699245712 Timestamp [UCT]: 2023-11-06 04:41:52 Age [y:d:h:m:s]: 01:139:15:20:45
Block: 885492 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360981 RingCT/type: yes/0
Extra: 0156a59fd37f752b7ddea91355f983625812bf7aa5e7a04b79b8335ca80743b69b02110000000733af99f4000000000000000000

1 output(s) for total of 0.714492087000 dcy

stealth address amount amount idx
00: 2e0ba9ac2390e927d7c48b746e1c2e7f9d385488f012b64c216e906582f9528d 0.714492087000 1341267 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": 885502, "vin": [ { "gen": { "height": 885492 } } ], "vout": [ { "amount": 714492087, "target": { "key": "2e0ba9ac2390e927d7c48b746e1c2e7f9d385488f012b64c216e906582f9528d" } } ], "extra": [ 1, 86, 165, 159, 211, 127, 117, 43, 125, 222, 169, 19, 85, 249, 131, 98, 88, 18, 191, 122, 165, 231, 160, 75, 121, 184, 51, 92, 168, 7, 67, 182, 155, 2, 17, 0, 0, 0, 7, 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