Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 771771fe24f23d92bdd53940c06b0a54304045534047337646779f3473c9b085

Tx prefix hash: 60b6207595983422ed06b4c5037de26a5f811780aff6699463d0d1e672f41a86
Tx public key: cc4cc8837ba23829d8c878d9b3c4a6c6bb82f8c8ee965de63461781a37a176d9
Timestamp: 1694836852 Timestamp [UCT]: 2023-09-16 04:00:52 Age [y:d:h:m:s]: 01:252:07:20:30
Block: 849125 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 441456 RingCT/type: yes/0
Extra: 01cc4cc8837ba23829d8c878d9b3c4a6c6bb82f8c8ee965de63461781a37a176d9021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.942966891000 dcy

stealth address amount amount idx
00: 95586eee130176f7c65d3331caf64c71e5bb1ea9770a8460d2ba5c90439616b9 0.942966891000 1302769 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": 849135, "vin": [ { "gen": { "height": 849125 } } ], "vout": [ { "amount": 942966891, "target": { "key": "95586eee130176f7c65d3331caf64c71e5bb1ea9770a8460d2ba5c90439616b9" } } ], "extra": [ 1, 204, 76, 200, 131, 123, 162, 56, 41, 216, 200, 120, 217, 179, 196, 166, 198, 187, 130, 248, 200, 238, 150, 93, 230, 52, 97, 120, 26, 55, 161, 118, 217, 2, 17, 0, 0, 0, 7, 230, 210, 127, 156, 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