Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4507d322a4a52741bcb3b0c2fd6ce3f3735e256231de9524d5861d97f0f18da1

Tx prefix hash: cef8eeae45976e7118dbd9747d05e483648e4acfe833e88f2432449ab496c890
Tx public key: 5fd3f8ed89d5ead90d0b1b5c999a0ec073f5a77a26592451d73c827d490fde50
Timestamp: 1638326043 Timestamp [UCT]: 2021-12-01 02:34:03 Age [y:d:h:m:s]: 03:152:07:00:50
Block: 385789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 887551 RingCT/type: yes/0
Extra: 015fd3f8ed89d5ead90d0b1b5c999a0ec073f5a77a26592451d73c827d490fde50021100000005d6e4826b000000000000000000

1 output(s) for total of 32.340283878000 dcy

stealth address amount amount idx
00: daaf0d1e33549036934cae3ce06a684d7e98e2ae2b8a0acbb0a0d48f263987b4 32.340283878000 778466 of 0

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": 385799, "vin": [ { "gen": { "height": 385789 } } ], "vout": [ { "amount": 32340283878, "target": { "key": "daaf0d1e33549036934cae3ce06a684d7e98e2ae2b8a0acbb0a0d48f263987b4" } } ], "extra": [ 1, 95, 211, 248, 237, 137, 213, 234, 217, 13, 11, 27, 92, 153, 154, 14, 192, 115, 245, 167, 122, 38, 89, 36, 81, 215, 60, 130, 125, 73, 15, 222, 80, 2, 17, 0, 0, 0, 5, 214, 228, 130, 107, 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