Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1037a02aa3dddc7d7921554d265445bea160e8ff72c87d93643fb493e6f6f2a4

Tx prefix hash: 8571145d2b01ad6b9002fd7c8e6bbdcfdb211617eb50533dc9158cbda7d834f9
Tx public key: 8a9520b6a599d48aa8d0007d73cc089ada419ff9cc8ead4aff0ff8962866a08a
Timestamp: 1710583638 Timestamp [UCT]: 2024-03-16 10:07:18 Age [y:d:h:m:s]: 01:015:00:51:44
Block: 979508 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271708 RingCT/type: yes/0
Extra: 018a9520b6a599d48aa8d0007d73cc089ada419ff9cc8ead4aff0ff8962866a08a021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 826e1787bd58944674ea04f64779ada411d32dbb36d5b18fc4903053d39db202 0.600000000000 1439543 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": 979518, "vin": [ { "gen": { "height": 979508 } } ], "vout": [ { "amount": 600000000, "target": { "key": "826e1787bd58944674ea04f64779ada411d32dbb36d5b18fc4903053d39db202" } } ], "extra": [ 1, 138, 149, 32, 182, 165, 153, 212, 138, 168, 208, 0, 125, 115, 204, 8, 154, 218, 65, 159, 249, 204, 142, 173, 74, 255, 15, 248, 150, 40, 102, 160, 138, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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