Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0231a7dd2149f6e73a78f1e1dfcf6d53c9f9feebdd903670e9fc0a241ea30730

Tx prefix hash: 5ed622ad15de65cc024d5fa8a3a9a6b6a893906ec0434bca4969852841d4267d
Tx public key: eab7eb37d84705519c038632e39fd3b7cc441aef323f901ab74ef1ccb059817a
Timestamp: 1707012695 Timestamp [UCT]: 2024-02-04 02:11:35 Age [y:d:h:m:s]: 01:002:18:17:01
Block: 949869 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262998 RingCT/type: yes/0
Extra: 01eab7eb37d84705519c038632e39fd3b7cc441aef323f901ab74ef1ccb059817a02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cdfe934fa7a3a920c6d2f613c6e8fe3157e8cf91ade437747fde901d9e873894 0.600000000000 1408403 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": 949879, "vin": [ { "gen": { "height": 949869 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cdfe934fa7a3a920c6d2f613c6e8fe3157e8cf91ade437747fde901d9e873894" } } ], "extra": [ 1, 234, 183, 235, 55, 216, 71, 5, 81, 156, 3, 134, 50, 227, 159, 211, 183, 204, 68, 26, 239, 50, 63, 144, 26, 183, 78, 241, 204, 176, 89, 129, 122, 2, 17, 0, 0, 0, 2, 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