Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37fd4094e2e658b5c81c32a7632c4f164fe3df8e98baaebc04fbfe15a86d6df3

Tx prefix hash: 870ea54e2ba00032c9fa0f28069ff834a5e90dc8e4e10a5c944fd325f87d0180
Tx public key: 425ca780d4d341f9ed3b30540015f324e9fd6f7b1e095080a91be691c62ef15e
Timestamp: 1727333786 Timestamp [UCT]: 2024-09-26 06:56:26 Age [y:d:h:m:s]: 00:251:20:25:02
Block: 1118357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179856 RingCT/type: yes/0
Extra: 01425ca780d4d341f9ed3b30540015f324e9fd6f7b1e095080a91be691c62ef15e021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26eb6d4358663122adb5bf7d15cb9e9e84f8b95cf6dbb6225dca86b21fa8ae99 0.600000000000 1599520 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": 1118367, "vin": [ { "gen": { "height": 1118357 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26eb6d4358663122adb5bf7d15cb9e9e84f8b95cf6dbb6225dca86b21fa8ae99" } } ], "extra": [ 1, 66, 92, 167, 128, 212, 211, 65, 249, 237, 59, 48, 84, 0, 21, 243, 36, 233, 253, 111, 123, 30, 9, 80, 128, 169, 27, 230, 145, 198, 46, 241, 94, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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