Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4ee56584af2298a52f7d4bac53e15d31a241e9f88f79a920966f6dd7fb1ad3f

Tx prefix hash: 6b82bc7e59f48a1820e4e6cb7f926d5ff75df9ceaa665b65748d3bbde79806a3
Tx public key: 3a50e951fba8a2ae98b7ddb693d0e950ddd61a7c955de4c614098dec3b3a18b3
Timestamp: 1743227354 Timestamp [UCT]: 2025-03-29 05:49:14 Age [y:d:h:m:s]: 00:284:05:59:54
Block: 1249635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200956 RingCT/type: yes/0
Extra: 013a50e951fba8a2ae98b7ddb693d0e950ddd61a7c955de4c614098dec3b3a18b30211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a2aedd3df2e14036d0cd6708b8b84e44ccbd64065beae721f26463ea7c3bdb9 0.600000000000 1736676 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": 1249645, "vin": [ { "gen": { "height": 1249635 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a2aedd3df2e14036d0cd6708b8b84e44ccbd64065beae721f26463ea7c3bdb9" } } ], "extra": [ 1, 58, 80, 233, 81, 251, 168, 162, 174, 152, 183, 221, 182, 147, 208, 233, 80, 221, 214, 26, 124, 149, 93, 228, 198, 20, 9, 141, 236, 59, 58, 24, 179, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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