Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c7f1a8f56f176d95f5cc6592b90dc102c13961c7bba1a025adff2f182562517

Tx prefix hash: 80423d21bb019b9e21295fae37152200c8ca922a85e6ed31c3b850f5c082d659
Tx public key: ec281fe833132d216290ea0b6ff9cc7bff60df224d09beba595f20f6b5b1051d
Timestamp: 1714094446 Timestamp [UCT]: 2024-04-26 01:20:46 Age [y:d:h:m:s]: 00:304:22:06:18
Block: 1008583 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217962 RingCT/type: yes/0
Extra: 01ec281fe833132d216290ea0b6ff9cc7bff60df224d09beba595f20f6b5b1051d02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b57acb55a9763a990871c459b601472e5c9b95762cd0952af23a57dbd8e62fe8 0.600000000000 1470055 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": 1008593, "vin": [ { "gen": { "height": 1008583 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b57acb55a9763a990871c459b601472e5c9b95762cd0952af23a57dbd8e62fe8" } } ], "extra": [ 1, 236, 40, 31, 232, 51, 19, 45, 33, 98, 144, 234, 11, 111, 249, 204, 123, 255, 96, 223, 34, 77, 9, 190, 186, 89, 95, 32, 246, 181, 177, 5, 29, 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