Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69b67ccfc2fbcf82b84a83764a534b638fdbdc419d3e8ffdf88fbdc05e57853e

Tx prefix hash: e8a428ed9d75393f41457c9347338896106468908d3edb48dabc5c6cf86bc87c
Tx public key: 3c06bf0cda32ac7535b1bf4a2aef1e790cdf3f364a7873418ed5df9475aea8cf
Timestamp: 1731374218 Timestamp [UCT]: 2024-11-12 01:16:58 Age [y:d:h:m:s]: 00:148:13:00:17
Block: 1151758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105993 RingCT/type: yes/0
Extra: 013c06bf0cda32ac7535b1bf4a2aef1e790cdf3f364a7873418ed5df9475aea8cf021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 952ebb70dd54b70c4845512cde302084f70ece1f8f98d17eea84e7addf33ef7b 0.600000000000 1637341 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": 1151768, "vin": [ { "gen": { "height": 1151758 } } ], "vout": [ { "amount": 600000000, "target": { "key": "952ebb70dd54b70c4845512cde302084f70ece1f8f98d17eea84e7addf33ef7b" } } ], "extra": [ 1, 60, 6, 191, 12, 218, 50, 172, 117, 53, 177, 191, 74, 42, 239, 30, 121, 12, 223, 63, 54, 74, 120, 115, 65, 142, 213, 223, 148, 117, 174, 168, 207, 2, 17, 0, 0, 0, 2, 0, 127, 151, 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