Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e52f79b5cb600b97b901f11912e261e6b074baf42e24b592b45693b01fb0575

Tx prefix hash: 67c2105e2e4f979064663eebe8aa0b2aab2750c256d7e44f64e35724f30f6b38
Tx public key: 11a0112829339da863be9bbdf68a0f853be50be7217b619e6a2c8b967126958f
Timestamp: 1634822144 Timestamp [UCT]: 2021-10-21 13:15:44 Age [y:d:h:m:s]: 03:086:08:58:36
Block: 357467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 839994 RingCT/type: yes/0
Extra: 0111a0112829339da863be9bbdf68a0f853be50be7217b619e6a2c8b967126958f0211000000014a0f5013000000000000000000

1 output(s) for total of 40.138750598000 dcy

stealth address amount amount idx
00: 8c14dbb75b77f7daa061bc48b2d695e12f7590ac14781bb9bbc098bcdfb55bae 40.138750598000 728899 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": 357477, "vin": [ { "gen": { "height": 357467 } } ], "vout": [ { "amount": 40138750598, "target": { "key": "8c14dbb75b77f7daa061bc48b2d695e12f7590ac14781bb9bbc098bcdfb55bae" } } ], "extra": [ 1, 17, 160, 17, 40, 41, 51, 157, 168, 99, 190, 155, 189, 246, 138, 15, 133, 59, 229, 11, 231, 33, 123, 97, 158, 106, 44, 139, 150, 113, 38, 149, 143, 2, 17, 0, 0, 0, 1, 74, 15, 80, 19, 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