Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cdf71c3f29339d5a26ea14a1566738e002452df7fe343e84e576dd3437e3f86

Tx prefix hash: d9f2eb1f3e88ea45c34c0e6ce6cc074e346dada9436c5b88193a2da8d378de6b
Tx public key: d50201ae8c642f10c99782a2e733ddbd44c634d6340e7b699d955ec85dba7066
Timestamp: 1681077202 Timestamp [UCT]: 2023-04-09 21:53:22 Age [y:d:h:m:s]: 02:000:10:31:51
Block: 735105 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 522475 RingCT/type: yes/0
Extra: 01d50201ae8c642f10c99782a2e733ddbd44c634d6340e7b699d955ec85dba70660211000000015029cbac000000000000000000

1 output(s) for total of 2.250568331000 dcy

stealth address amount amount idx
00: 5c660ea81df4f301e1b915369314ee5726ad4c925c7bdb308398abd5a845f58d 2.250568331000 1181396 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": 735115, "vin": [ { "gen": { "height": 735105 } } ], "vout": [ { "amount": 2250568331, "target": { "key": "5c660ea81df4f301e1b915369314ee5726ad4c925c7bdb308398abd5a845f58d" } } ], "extra": [ 1, 213, 2, 1, 174, 140, 100, 47, 16, 201, 151, 130, 162, 231, 51, 221, 189, 68, 198, 52, 214, 52, 14, 123, 105, 157, 149, 94, 200, 93, 186, 112, 102, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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