Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f75f864fef8fbd66fc310075f0dcf4ea7c63a07c90f6e3087b657fbf5d22d58f

Tx prefix hash: b06dc7f52cfc0b27b569bcd4af7ec12e80ab45d6a5cf0a11fad96e1e5147d9e1
Tx public key: b6689d33ec9ce7a0fff1483171d6d8b1de38f4aca463c725f82459c64565a8c0
Timestamp: 1593017659 Timestamp [UCT]: 2020-06-24 16:54:19 Age [y:d:h:m:s]: 04:154:11:30:20
Block: 110464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1050692 RingCT/type: yes/0
Extra: 01b6689d33ec9ce7a0fff1483171d6d8b1de38f4aca463c725f82459c64565a8c002110000002e46a11e8a000000000000000000

1 output(s) for total of 264.233367466000 dcy

stealth address amount amount idx
00: 4c80cae8a292659fcfced7994ebc6e843499e74bedaf295fd551b8c47d50e1f6 264.233367466000 191348 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": 110474, "vin": [ { "gen": { "height": 110464 } } ], "vout": [ { "amount": 264233367466, "target": { "key": "4c80cae8a292659fcfced7994ebc6e843499e74bedaf295fd551b8c47d50e1f6" } } ], "extra": [ 1, 182, 104, 157, 51, 236, 156, 231, 160, 255, 241, 72, 49, 113, 214, 216, 177, 222, 56, 244, 172, 164, 99, 199, 37, 248, 36, 89, 198, 69, 101, 168, 192, 2, 17, 0, 0, 0, 46, 70, 161, 30, 138, 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