Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d057ed05ef76d1261ddde4f9b13cfd59c51f20b20c025eb802aa10801535cef

Tx prefix hash: 65900e308c160deb698d39a595c3cb510e7366a52d53d539261ec6713e2e2251
Tx public key: 7d24b7ccca7aafa1d55d4f900c1941017c3a85eb94397f15c4ff29cd47a70b77
Timestamp: 1703747935 Timestamp [UCT]: 2023-12-28 07:18:55 Age [y:d:h:m:s]: 01:315:19:52:06
Block: 922823 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 484550 RingCT/type: yes/0
Extra: 017d24b7ccca7aafa1d55d4f900c1941017c3a85eb94397f15c4ff29cd47a70b7702110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30e6d96d34a0ae4ff9c7bc43f67a9c4b9b547428829fc203476d8c093e826fea 0.600000000000 1380527 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": 922833, "vin": [ { "gen": { "height": 922823 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30e6d96d34a0ae4ff9c7bc43f67a9c4b9b547428829fc203476d8c093e826fea" } } ], "extra": [ 1, 125, 36, 183, 204, 202, 122, 175, 161, 213, 93, 79, 144, 12, 25, 65, 1, 124, 58, 133, 235, 148, 57, 127, 21, 196, 255, 41, 205, 71, 167, 11, 119, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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