Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de482a36c6154402ef71c06d7412aa277d1bdafdcb694fdb7b1da9c602ffb496

Tx prefix hash: 4635b5492783733e42cf9a3e4ffe32505db5b6043e0c19e3136be3a4032e3679
Tx public key: dd9b1550cdf6fd7b10aaf1cdbcb3382555295c14f52d411fee9ff83c55dd4994
Timestamp: 1709058662 Timestamp [UCT]: 2024-02-27 18:31:02 Age [y:d:h:m:s]: 01:042:09:15:22
Block: 966852 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291308 RingCT/type: yes/0
Extra: 01dd9b1550cdf6fd7b10aaf1cdbcb3382555295c14f52d411fee9ff83c55dd499402110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be6ba834c68bb060dc7ee5bd4b1dbe903122c3fe2e23710afbd1760ba8c4dc26 0.600000000000 1426623 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": 966862, "vin": [ { "gen": { "height": 966852 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be6ba834c68bb060dc7ee5bd4b1dbe903122c3fe2e23710afbd1760ba8c4dc26" } } ], "extra": [ 1, 221, 155, 21, 80, 205, 246, 253, 123, 16, 170, 241, 205, 188, 179, 56, 37, 85, 41, 92, 20, 245, 45, 65, 31, 238, 159, 248, 60, 85, 221, 73, 148, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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